d/xen-utils-common.xen.init: disable oom killer for xenstored
authorHans van Kranenburg <hans@knorrie.org>
Sun, 6 Sep 2020 20:54:15 +0000 (22:54 +0200)
committerHans van Kranenburg <hans@knorrie.org>
Mon, 21 Sep 2020 22:33:14 +0000 (00:33 +0200)
commit15b0b154f99ee6a853825eb0df83c9fb6cbe2e0a
tree659efc541f4e2275d06a657d2e710e37cf1905b6
parentea51288b94431224a27c80307c69e3b47f5c61e5
d/xen-utils-common.xen.init: disable oom killer for xenstored

In case of oom killer terminating some process, we'd rather not see
xenstored go. Xenstored has an in-memory database, and when starting the
process again, it would be empty, which is very inconvenient. Xenstored
should already score quite low and have a fairly low memory footprint,
but according to the user report, it happened.

Closes: #961511
Suggested-by: Samuel Thibault <sthibault@debian.org>
Signed-off-by: Hans van Kranenburg <hans@knorrie.org>
Acked-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
debian/xen-utils-common.xen.init